Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency reflect-metadata to v0.2.2 #209

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency reflect-metadata to v0.2.2 #209

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
reflect-metadata (source) 0.1.13 -> 0.2.2 age adoption passing confidence

Release Notes

rbuckton/reflect-metadata (reflect-metadata)

v0.2.2

Compare Source

v0.2.1

Compare Source

What's Changed

Full Changelog: rbuckton/reflect-metadata@v0.2.0...v0.2.1

v0.2.0: reflect-metadata 0.2.0

Compare Source

What's Changed

Full Changelog: rbuckton/reflect-metadata@v0.1.14...v0.2.0

v0.1.14

Compare Source

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 29, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"7.6.18" from the root project
npm ERR!   peer @nestjs/common@"^7.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"7.6.18" from the root project
npm ERR!     3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR!   3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"7.6.18" from the root project
npm ERR!     peer @nestjs/common@"^7.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"7.6.18" from the root project
npm ERR!       3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR!     3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-06T04_42_16_586Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from dc1c9f3 to e4457ea Compare May 6, 2024 04:42
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from e4457ea to ddce26c Compare May 13, 2024 04:39
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 13, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"7.6.18" from the root project
npm ERR!   peer @nestjs/common@"^7.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"7.6.18" from the root project
npm ERR!     3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR!   3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"7.6.18" from the root project
npm ERR!     peer @nestjs/common@"^7.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"7.6.18" from the root project
npm ERR!       3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR!     3 more (@nestjs/mongoose, @nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-02-17T04_37_17_927Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from ddce26c to 836ea76 Compare May 20, 2024 11:38
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 836ea76 to 353446f Compare November 11, 2024 04:40
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 353446f to 3c4fe97 Compare November 18, 2024 04:52
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 55ac0b9 to 2f19ba0 Compare December 2, 2024 03:52
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 35e42fb to 7bdfed7 Compare January 27, 2025 06:37
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 7bdfed7 to 7c7fefa Compare February 3, 2025 06:12
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 7c7fefa to dd96e11 Compare February 10, 2025 07:07
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from dd96e11 to 2437d68 Compare February 17, 2025 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants